Release 10.1A: OpenEdge Development:
Progress Dynamics Managers API Reference

Overview

The Profile Manager encapsulates all user profile access supported by the framework. User profile data includes such run-time information as the user’s preferences for window positions and sizes, browser filter settings, and report filter settings. It also includes systemwide information, such as ToolTips enabled and similar UI options. The Profile Manager stores all of these settings by user. The user can decided to save the settings only for the current session or save them permanently in the Repository for consistency between client sessions.

In a distributed environment, the Profile Manager is started on both the client and server sides. There is a wrapper program for each side that sets the global variable, server-side, to either YES for the server-side version or NO for the client-side version. Both programs then include the main code of the manager from the af\app\afpromngrp.i include file. The differences in how the manager operates on each side are triggered by checking the value of the server-side variable.

The Profile Manager’s handle is stored in the global shared variable, gshProfileManager.

Table 6–1 shows the files that contain the Profile Manager’s code.

Table 6–1: Profile Manager files

Type	Path
Client-side wrapper	af\sup2\afproclntp.p
Server-side wrapper	af\app\afprosrvrp.p
Main code	af\app\afpromngrp.i
Included files	af\app\afbldclicp.p af\app\afproupdcadbp.i af\app\afttprofiledata.i af\sup2\afcheckerr.i af\sup2\aferrortxt.i af\sup2\afglobals.i

For more information on this Manager, see the chapter on using the Progress Dynamics Managers in OpenEdge Development: Progress Dynamics Advanced Development .